home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20030409-20031118
/
000024_JDanSkinner@JDanSkinner.com_Tue Apr 29 09:41:49 EDT 2003.msg
< prev
next >
Wrap
Text File
|
2020-01-01
|
3KB
|
63 lines
Article: 14240 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!phl-feed.news.verio.net!iad-feed.news.verio.net!iad-peer.news.verio.net!news.verio.net!news.maxwell.syr.edu!newsfeed.stanford.edu!postnews1.google.com!not-for-mail
From: JDanSkinner@JDanSkinner.com (Dan Skinner)
Newsgroups: comp.protocols.misc,comp.protocols.kermit.misc,comp.protocols.ppp
Subject: Re: Communication protocol for direct serial link (null-modem or similar)?
Date: 28 Apr 2003 16:46:24 -0700
Organization: http://groups.google.com/
Lines: 44
Message-ID: <8ce22d01.0304281546.7fcd7cdf@posting.google.com>
References: <3R6qa.6946$b71.104830@news4.e.nsc.no>
NNTP-Posting-Host: 24.159.192.106
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1051573585 26283 127.0.0.1 (28 Apr 2003 23:46:25 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 28 Apr 2003 23:46:25 GMT
Xref: newsmaster.cc.columbia.edu comp.protocols.misc:9760 comp.protocols.kermit.misc:14240 comp.protocols.ppp:39864
Toralf Lund <toralf-delete-this@procaptura.com> wrote in message news:<3R6qa.6946$b71.104830@news4.e.nsc.no>...
> I'm looking for a protocol that may be used for simple communication
> across a direct serial link - RS232 using null-modem cable or similar -
> between a Linux host and a simple (old) IPC (Intelligent Peripheral
> Controller) board.
>
> The IPC has no real OS, just a simple, custom kernel, and rather limited
> development support, so the protocol needs to be simple to implement.
> Also, the system is really low-end by today's standards - it's has a
> 12.5Mhz MC68010 CPU and 1Mb RAM - so the runtime must be fairly small and
> efficient.
>
> The link will be used only to send simple packets ("commands") to the IPC,
> and status from the IPC back to the Linux system; there will be no file
> transfers or anything.
>
> Protocols I've considered:
> - Kermit
> - AHDLC/LAPB (as utilised e.g. by PPP) - X/Y/Z-modem
>
> What would you people out there recommend choosing? And does anyone know
> of any good example source code that may help me get started? I'm
> primarily interested in a nice and isolated implementation of the packet
> communication itself, i.e. source code without all the additional bits
> normally found in comms packages, like UI operations, file I/O, modem dial
> etc., which I don't need (and I don't want them there to confuse
> everything.)
I may be missing the point, but sounds to me like plain old full
duplex
RS232 is all you need. We all ran terminal sessions on Unix and other
hosts
using this non-protocol for years. The non-reliability of this hook
up would
show up as a typo, although the error may have been the key struck,
the sending of the key, the receipt of the key, the echo of the key,
or the receipt of the
echo. We fixed it with backspace (rubout) an ended up with machine b
understanding exactly what machine a wanted to send. We even managed
to send strings of some length in this environment. I even use this
kind of connection
to automatically start kermit file transfers over modem circuts now.
Regards...Dan.